WelcomeText1 = As part of a Year 2000 Audit your Network Administrator has identified some data files on your computer which contain dates that may cause problems on or after the Year 2000.\n\nUse the Date Explorer to examine the potential problems. The Date Explorer helps you navigate directly to the problem data.
WelcomeText2 = To examine the problem data you should:\n\n1. Select the data file to review\n\nDouble click the file, or highlight the file in the list and choose Open. The Cell Explorer loads.
WelcomeText3 = 2. Use the Cell Explorer to navigate your data file and then correct any problematic dates.\n\nThe Cell Explorer displays the list of cells in your data file containing dates that may cause a problem on or after the Year 2000. Double clicking on one of the entries in the list launches the application and takes you to the cell where the problem lies.
WelcomeText4 = 3. Change the File Status of the data file.\n\nWhen you have finished reviewing a data file, change the File Status to reflect the Year 2000 compliance of the file. You can do this either from the File Status dropdown list in the Cell Explorer or by right clicking the entry in the Date Explorer. The File Status is returned to your Network Administrator so that the progress of the review can be monitored as part of the Year 2000 Audit.
WelcomeText5 = Use the Help button on the Date Explorer window to get more information about this program and about potential Year 2000 problems.
ExcelTip1=A two digit year in the range 00 to 19 is calculated to be 2000 to 2019 by Excel, (later versions assume 00 to 29 as being 2000 through 2029). A two digit year may have been imported to a four digit format and interpreted incorrectly. A date prior to 1920 may be correct, but you are recommended to examine it.
ExcelTip2=A custom date format in Excel is being used resulting in a two digit year. It is recommended that the date format is changed to use a four digit year.
ExcelTip3=The date is handled correctly within Excel, but may cause a problem if exported, as the century may not be correctly interpreted by another application. It is recommended the Windows short date format be changed to use a four digit year.
ExcelTip4=Examine the cell to see if 1900 is being used as a date or date offset.
ExcelTip5=A function given a two digit year may interpret the century incorrectly and produce unexpected results. It is recommended that this date be changed to a four digit year, or the cell usage be examined.
ExcelTip6=If the derived value is a two digit year unexpected results could occur. It is recommended that you ensure the value is a four digit year, or examine the usage of this cell.
ExcelTip7=A two digit year used in a calculation could cause an unexpected result. It is recommended that a four digit year is used.
ExcelTip8=This file could not be scanned because it is password protected. If you want to scan the file now, use Excel to remove the password and then reopen the file from the Date Explorer.
ExcelTip9=This file contains one or more Visual Basic macros that cannot be scanned, and therefore could cause a potential problem. You are recommended to examine the use of these macros. (The rest of the file has been scanned and any potential problems are reported separately.)
ExcelTip11=The Centennial 2000 scanner was unable to scan this file. This may be because you do not have rights to open the file or because it is not a valid Excel worksheet. Open the file with Excel to check it.
L123Tip1=All two digit years are calculated to be 1900 to 1999 by 1-2-3, (later versions assume 00 to 49 as being 2000 through 2049). A two digit year may have been imported to a four digit format and interpreted incorrectly. A date prior to 1920 may be correct, but you are recommended to examine it.
L123Tip2=A custom date format is being used resulting in a two digit year. It is recommended that the date format is changed to use a four digit year.
L123Tip3=The date is handled correctly within 1-2-3, but may cause a problem if exported, as the century may not be correctly interpreted by another application. It is recommended the Windows short date format be changed to use a four digit year.
L123Tip4=Examine the cell to see if 1900 is being used as a date or date offset.
L123Tip5=A function given a two digit year may interpret the century incorrectly and produce unexpected results. It is recommended that this date be changed to a four digit year, or the cell usage be examined.
L123Tip6=If the derived value is a two digit year unexpected results could occur. It is recommended that you ensure the value is a four digit year, or examine the usage of this cell.
L123Tip7=A two digit year used in a calculation could cause an unexpected result. It is recommended that a four digit year is used.
L123Tip8=This file could not be scanned because it is password protected. If you want to scan the file now, use 1-2-3 to remove the password and then reopen the file from the Date Explorer.
L123Tip11=The Centennial 2000 scanner was unable to scan this file. This may be because you do not have rights to open the file or because it is not a valid 1-2-3 worksheet. Open the file with 1-2-3 to check it.
QProTip1=All two digit years are calculated to be 1900 to 1999 by Quattro Pro. A two digit year may have been imported to a four digit format and interpreted incorrectly. A date prior to 1920 may be correct, but you are recommended to examine it.
QProTip2=A custom date format is being used resulting in a two digit year. It is recommended that the date format is changed to use a four digit year.
QProTip3=The date is handled correctly within Quattro Pro, but may cause a problem if exported, as the century may not be correctly interpreted by another application. It is recommended the Windows short date format be changed to use a four digit year.
QProTip4=Examine the cell to see if 1900 is being used as a date or date offset.
QProTip5=A function given a two digit year may interpret the century incorrectly and produce unexpected results. It is recommended that this date be changed to a four digit year, or the cell usage be examined.
QProTip6=If the derived value is a two digit year unexpected results could occur. It is recommended that you ensure the value is a four digit year, or examine the usage of this cell.
QProTip7=A two digit year used in a calculation could cause an unexpected result. It is recommended that a four digit year is used.
QProTip8=This file could not be scanned because it is password protected. If you want to scan the file now, use Quattro Pro to remove the password and then reopen the file from the Date Explorer.
QProTip11=The Centennial 2000 scanner was unable to scan this file. This may be because you do not have rights to open the file or because it is not a valid Quattro Pro worksheet. Open the file with Quattro Pro to check it.
AccessTip1=A two digit year in the range 00 to 19 is calculated to be 2000 to 2019 by Access, (later versions assume 00 to 29 as being 2000 through 2029). A two digit year may have been imported to a four digit format and interpreted incorrectly. A date prior to 1920 may be correct, but you are recommended to examine it.
AccessTip2=A custom date format in Access is being used resulting in a two digit year. It is recommended that the date format is changed to use a four digit year.
AccessTip3=The date is handled correctly within Access, but may cause a problem if exported, as the century may not be correctly interpreted by another application. It is recommended the Windows short date format be changed to use a four digit year.
AccessTip7=A two digit year used in a calculation could cause an unexpected result. It is recommended that a four digit year is used.
AccessTip8=This file could not be scanned because it is password protected. If you want to scan the file now, use Access to remove the password and then reopen the file from the Date Explorer.
AccessTip9=This file contains one or more Visual Basic macros that cannot be scanned, and therefore could cause a potential problem. You are recommended to examine the use of these macros. (The rest of the file has been scanned and any potential problems are reported separately.)
AccessTip10=It is recommended that an Input Mask is used to force a four digit year to be input.
AccessTip11=The Centennial 2000 scanner was unable to scan this file. This may be because you do not have rights to open the file or because it is not a valid Access database. Open the file with Access to check it.
CSVTip1=A two digit year in the range 00 to 19 is calculated to be 2000 to 2019 by some applications. A two digit year may be imported to a four digit format and interpreted incorrectly. A date prior to 1920 may be correct, but you are recommended to examine it.
CSVTip2=It is recommended that the date is changed to use a four digit year.
CSVTip11=The Centennial 2000 scanner was unable to scan this file. This may be because you do not have rights to open the file or because it is not a valid Comma Separated Value file. Open the file with Notepad to check it.
DBFTip1=A two digit year in the range 00 to 19 is calculated to be 2000 to 2019 by some applications. A two digit year may be imported to a four digit format and interpreted incorrectly. A date prior to 1920 may be correct, but you are recommended to examine it.
DBFTip2=It is recommended that the date is changed to use a four digit year.
DBFTip8=This file could not be scanned because it is password protected. If you want to scan the file now, use FoxPro/dBASE to remove the password and then reopen the file from the Date Explorer.
DBFTip11=The Centennial 2000 scanner was unable to scan this file. This may be because you do not have rights to open the file or because it is not a valid FoxPro/dBASE database. Open the file with FoxPro/dBASE to check it.
ODBCTip1=A two digit year in the range 00 to 19 is calculated to be 2000 to 2019 by some applications. A two digit year may be imported to a four digit format and interpreted incorrectly. A date prior to 1920 may be correct, but you are recommended to examine it.
ODBCTip2=It is recommended that the date is changed to use a four digit year.
ODBCTip11=The Centennial 2000 scanner was unable to scan this ODBC Data Source. This may be because you do not have rights to open the Data Source database.
